Date: Wed, 22 Sep 2004 02:30:54 +0900 From: Hajimu UMEMOTO <ume@FreeBSD.org> To: Thomas Quinot <thomas@FreeBSD.ORG> Cc: freebsd-net@freebsd.org Subject: Re: freeaddrinfo(NULL) Message-ID: <ygefz5bh6lt.wl%ume@FreeBSD.org> In-Reply-To: <20040921123016.GA41677@melusine.cuivre.fr.eu.org> References: <20040921123016.GA41677@melusine.cuivre.fr.eu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, >>>>> On Tue, 21 Sep 2004 14:30:16 +0200 >>>>> Thomas Quinot <thomas@FreeBSD.ORG> said: thomas> Currently a call to freeaddrinfo (NULL) causes a segfault. Is there any thomas> reason why we should not make that a no-op? This would make freeaddrinfo thomas> behave in a manner consistent with free(3), and also with what happens thomas> on Linux. Because, the behavior of freeaddrinfo (NULL) is undefined in RFC 2553 nor RFC 3493. Having such an assumption is a potentially bug and lose portability. Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ygefz5bh6lt.wl%ume>